chore: bump contract #65
Conversation
tests/testdata/version.txt
Outdated
| v0.11.0-rc.1 | ||
| 16f615403c89b2a49a656ae199cd2ba19e963f00 |
There was a problem hiding this comment.
Better to bump this to current main (5f5ba8de0f04fc807a2c5683ab49235c8514cfc9).
Either that, or (better) tag / release a new v0.12.0-rc.0 of the contracts.
There was a problem hiding this comment.
We have something like circular deps here:
babylon<-babylon-sdk(version / tag for docker)babylon-sdk<-babylon-contract(version / tag for contracts)babylon-contract<-babylon(submodule for protos)
Which is unfortunate, but kind of unavoidable at this point I guess.
There was a problem hiding this comment.
Sequence of versioning would be:
- Release new contracts version / tag. With the
babylonsubmodule pointing to a babylon dev branch if necessary. - Release a
babylon-sdkversion / tag with that contract version. - Integrate that babylon sdk with babylon and other repos (integration, tests, etc.)
- Adjust / update the babylon submodule ref in
babylon-contracttobase/consumer-chain-support. (inmainor in a new branch)
There was a problem hiding this comment.
Yep we might need to start defining some release process, as well as cleaning the dependencies.
My current thinking is to follow phase-2's procedure where Babylon remains the root of the dependency. The process is then like releasing Babylon node -> releasing every peripheral program.
This requires us to move out all the e2e tests for integration from Babylon to Babylon SDK.
Wdyt we create a github issue for the release procedure, and then address it after moving out those e2e tests from Babylon?
No description provided.